Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1662

reference: 472-tree-1
name: 1662
tree-preservation-order: undefined
472-tpo-1
uprn
address-text
point: POINT (-1.023752 50.882642)
geometry: MULTIPOLYGON (((-1.023710 50.882637,-1.023712 50.882646,-1.023717 50.882653,-1.023727 50.882659,-1.023739 50.882663,-1.023752 50.882665,-1.023777 50.882660,-1.023786 50.882654,-1.023793 50.882646,-1.023795 50.882638,-1.023793 50.882630,-1.023787 50.882622,-1.023778 50.882616,-1.023766 50.882612,-1.023753 50.882611,-1.023740 50.882612,-1.023718 50.882621,-1.023712 50.882629,-1.023710 50.882637)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL